Date-warning: Date header was inserted by AdminA.RFERL.Org
Date: 2 Jun 94 12:04:46 GMT
X-Sender: waldorfm@muvaxb.rferl.org
Message-ID: <9406020504.aa14546@q2.ics.uci.edu>
Content-type: text/plain; charset="us-ascii"
MIME-version: 1.0
Newsgroups: fa.think-c
>I'm sure an experienced programmer can answer this one without even writing a
>flow chart....
>
>I wrote an extention that works exactly as I need it to. It does not,
>however, display the Icon at startup at the bottom of the screen. The icon
>itself is defined correctly. When looking at it through the finder, the Icon
>appears correctly
>
>I assume there is some simple code to remidy this(?)
I have some easy to implement sample source code (ThinkC) which will show specified Icon resources at startup. I cannot remember where I got it from, but I could send you the files. Let me now what format you can handle.
>From nagel@wahoo.rdatasys.com Mon, 20 Jun 1994 19:01:00 PDT
Return-Path: nagel@wahoo.rdatasys.com
Received: from wahoo.rdatasys.com (nagel@wahoo.rdatasys.com [198.137.184.2]) by wahoo.rdatasys.COM (8.6.9/8.6.9) with ESMTP id TAA06882 for <think-c@wahoo.rdatasys.com>; Mon, 20 Jun 1994 19:01:03 -0700
To: think-c@wahoo.rdatasys.com
Subject: test message
Reply-To: mark.nagel@rdatasys.com
Organization: Relational Data Systems, Irvine, CA
Phone: (714) 263-3899
Date: Mon, 20 Jun 1994 19:01:00 PDT
Message-ID: <6874.772164060@wahoo.rdatasys.com>
From: "Mark D. Nagel" <nagel@wahoo.rdatasys.com>
Hi all. I'm testing the new list processing software on
rdatasys.com. Assuming all goes well, I will switch over to this
system within a few days. There may be some glitches at first as
everything gets settled in, but I'm sure it will last only a short
Does anyone know of any example code that implements finder
triangles?
--Kevin - omalley@umich.edu
>From nagel@rdatasys.com Wed, 22 Jun 1994 12:16:42 PDT
Return-Path: nagel@rdatasys.com
Received: from rdatasys.com (nagel@wahoo.rdatasys.com [198.137.184.2]) by wahoo.rdatasys.COM (8.6.9/8.6.9) with ESMTP id MAA04052 for <think-c@rdatasys.com>; Wed, 22 Jun 1994 12:16:44 -0700
To: think-c@rdatasys.com
Subject: test message #2
Reply-To: mark.nagel@rdatasys.com
Organization: Relational Data Systems, Irvine, CA
Phone: (714) 263-3899
Date: Wed, 22 Jun 1994 12:16:42 PDT
Message-ID: <4049.772312602@rdatasys.com>
From: "Mark D. Nagel" <nagel@rdatasys.com>
Testing system with just my own name in the list...
--------
Mark D. Nagel <mark.nagel@rdatasys.com> Relational Data Systems
30 Executive Park, Suite 260
Eat right. Exercise. Die anyway. Irvine, CA 92714
(714) 263-3899
>From nagel@rdatasys.com Wed Jun 22 12:25:03 1994
Received: from rdatasys.com (nagel@wahoo.rdatasys.com [198.137.184.2]) by wahoo.rdatasys.COM (8.6.9/8.6.9) with ESMTP id MAA04289 for <think-c@rdatasys.com>; Wed, 22 Jun 1994 12:25:02 -0700
Received: from rdatasys.com (nagel@wahoo.rdatasys.com [198.137.184.2]) by wahoo.rdatasys.COM (8.6.9/8.6.9) with ESMTP id MAA04470 for <think-c@rdatasys.com>; Wed, 22 Jun 1994 12:33:32 -0700
Received: from rdatasys.com (nagel@wahoo.rdatasys.com [198.137.184.2]) by wahoo.rdatasys.COM (8.6.9/8.6.9) with ESMTP id SAA08444 for <think-c@rdatasys.com>; Wed, 22 Jun 1994 18:08:48 -0700
To: think-c@rdatasys.com
Subject: ANNOUNCE: The list has moved!
Reply-To: mark.nagel@rdatasys.com
Organization: Relational Data Systems, Irvine, CA
Phone: (714) 263-3899
Date: Wed, 22 Jun 1994 18:08:45 PDT
Message-ID: <8441.772333725@rdatasys.com>
From: "Mark D. Nagel" <nagel@rdatasys.com>
You read it here first; the think-c list has moved from ics.uci.edu
to rdatasys.com. Messages sent to ics.uci.edu will start being
forwarded to the new list within a few days. I will keep the lists
in sync until then, but everyone should start using the new address
immediately.
To send messages to the list, send to think-c@rdatasys.com. If you
try to send a message and cannot because you are told you are not on
the list, please let me know. This is a feature of the software
that might need fine tuning for some folks.
You may send requests to think-c-request@rdatasys.com, but you'll
receive a message explaining how to actually do things now :).
To perform administrative changes, like subscribe, unsubscribe,
etc., send all messages to listproc@rdatasys.com. I'm including the
message you'd receive from think-c-request below which should
explain how to do the most common things.
The archive is still on ftp.ics.uci.edu for now, but I will be
moving it within the next week. When it is all ready, I will let
the list know.
Here is the message you'd receive from think-c-request:
This mailing list is now under the control of automated subscription
software. To subscribe, please send email to the address:
listproc@rdatasys.com
with a blank Subject line and the command:
SUBSCRIBE <list_name> Your Name
in the message body. Listname would be the name of the mailing list
you wish to subscribe to (for instance "think-c") and should not be
the full email address of th list (do not use
"think-c@rdatasys.com"). The name should be your real name, not
your email address. An example is:
SUBSCRIBE think-c Mark D. Nagel
If you want a list of commands you can use with the listproc
software, send it a command of "help". If you want to see what
mailing lists can be accessed through "listproc@rdatasys.com", send
it a command of "lists".
If nothing else works, send mail to "server@rdatasys.com" and
eventually a real human will see it (emphasis on eventually).
For your reference, a quick tutorial on using listproc is appended
to this message.
Thank you for your cooperation.
Thanks also to Chuq Von Rospach for the message from which this one
was derived.
Mark D. Nagel
Relational Data Systems, Product Development Manager
Mailing List Administrator
+_+_+_+_+_+_+_+_++
The quick and easy 30 second guide to listproc
(for people who hate reading the instructions)
Listproc is a mailing list and archiving system that is similar to,
but not identical with, the BITNET LISTSERV software. If you take the
time to learn a few simple command, you'll find it a powerful and
flexible way to find and access the information that has been made
available. Listproc, however, is stupid. If you don't send it exactly
what it wants to see, it'll make you miserable.
Fortunately, it is pretty simple to feed the listproc. Just follow
the directions.
All listproc commands are sent to the address listproc@rdatasys.com
as an email message. The commands should be in the body of the
message, not the Subject line. In fact, if you attempt to put
commands in the Subject line, listproc will reject your message and
return it. LEAVE THE SUBJECT LINE BLANK. If your mail software won't
let you do that, put something cute and innovative in there instead.
Whatever you do, don't put listproc commands in the Subject line!
If you remember that piece of advice, 99% of your problems with
listproc are solved.
Listproc has two major subsystems: the mailing list subsystem and the
archive subsystem.
There is one command all listproc users should know: HELP. You can
give it a parameter of COMMAND, where COMMAND is one of the listproc
commands, and listproc will send you more details on that command.
Mailing List Commands
There are four commands commonly used to control the mailing list
subsystem:
LISTS: The LISTS command takes no parameters. It will cause
listproc to send you the names of the mailing lists supported by this
server.
SUBSCRIBE: enrolls you in a mailing list. The format is:
SUBSCRIBE LISTNAME YOURNAME. LISTNAME is the name of the mailing
list. YOURNAME is, not surprisingly, your real name, not your email
address, which listproc will get from the header of the email
message.
UNSUBSCRIBE: removes you from a mailing list. The format is
UNSUBSCRIBE LISTNAME. You don't give your name to the UNSUBCRIBE
command.
SET: The SET command lets you change the options attached to
your subscription on a list. The format is SET LISTNAME MAIL <option>.
The common options are DIGEST, ACK and NOACK.
DIGEST converts your subscription to the digest format, which
means that instead of getting individual messages as they are sent to
listproc, you would get them in a combined format, usually once a
day, in a single mail message. This option is very useful to people
suffering from too much email.
ACK and NOACK turn off the digest format and cause listproc to
send you individual messages again. The difference between the two is
how listproc handles your own submissions to the list. ACK will cause
listproc to send you a copy of your own messages, while NOACK won't.
The default is typically ACK.
There are other commands and options that can be used as well, and
these are covered in the on-line documentation available through the
HELP command.
In summary, here's how a typical listproc command would look that
uses these commands. This assumes UCB mail, but other mailers will
work the same way:
% mail listproc@rdatasys.com
Subject: remember, we don't put listproc commands here
HELP
HELP SET
LIST
SUBSCRIBE think-c Mark D. Nagel
SET think-c MAIL DIGEST
SUBSCRIBE other-list Mark D. Nagel
UNSUBSCRIBE other-list
SET think-c MAIL NOACK
^D
%
Archive Server Commands
The archive server allows you to receive copies of files stored in
the archive. This service is similar to FTP, but doesn't require that
a user have access to anything but electronic mail.
To find out what is available in the archive, you use the INDEX
command. Archives can be nested, and to get information on listed
sub-archives. An example of doing this would look like this:
% mail listproc@rdatasys.com
Subject: This space left blank, of course
INDEX
INDEX think-c
INDEX think-c/digests
^D
%
This will return you three mail messages, one with the master index,
one with the index for the mae-users list, and one for the digests
sub-archive in mae-users. The way this listproc is configured, all
messages submitted to a list are compiled into digests and stored in
the archives in the digests sub-archive, which means it's possible to
locate and recover previous messages.
To have listproc send you a file, you use the GET command. The format
is GET ARCHIVE FILENAME.
An example of this would be:
% mail listproc@rdatasys.com
Subject: remember, this is blank!
GET think-c/digests 94Apr27
^D
%
This will return the file in an email message. If the file is long,
it might be split into multiple pieces. Binary files will be encoded
in a format to allow them to be mailed.
The SEARCH command allows you to locate specific pieces of
information within the archive. It allows you to 'grep' the archives.
This is especially useful if you're trying to locate a specific topic
in the digests, or, say, copy of one of your postings. The format of
the SEARCH command is SEARCH ARCHIVE SEARCHSTRING.
An example of this is:
% mail listproc@rdatasys.com
Subject: do I really have to say it?
SEARCH think-c/digests "Mark D. Nagel"
SEARCH think-c server
^D
%
With these commands, you can do the common actions you want out of a
listproc. If you want to learn more about listproc, please send it
the HELP command and start reading the on-line documentation.
If you have any problems with the listproc, please send mail to
server@rdatasys.com.
--------
Mark D. Nagel <mark.nagel@rdatasys.com> Relational Data Systems
30 Executive Park, Suite 260
Eat right. Exercise. Die anyway. Irvine, CA 92714
(714) 263-3899
>From rhartman@dsl2.uoregon.edu Thu Jun 23 11:04:51 1994
Received: from lionfish.rdatasys.com (uucp@lionfish.rdatasys.com [198.232.168.1]) by wahoo.rdatasys.COM (8.6.9/8.6.9) with ESMTP id LAA19395 for <think-c@rdatasys.com>; Thu, 23 Jun 1994 11:04:51 -0700
Received: (from uucp@localhost) by lionfish.rdatasys.com (8.6.9/8.6.9) id LAA08528 for <think-c@rdatasys.com>; Thu, 23 Jun 1994 11:04:49 -0700
Received: from dsl2.uoregon.edu(128.223.108.147) by lionfish.rdatasys.com via smap (V1.3mjr)
id sma008524; Thu Jun 23 11:03:54 1994
Received: from rhartman.symantec.com by dsl2.uoregon.edu (NX5.67c/NX3.0M)
id AA00794; Thu, 23 Jun 94 11:03:40 -0700
Message-Id: <9406231803.AA00794@dsl2.uoregon.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 23 Jun 1994 11:03:43 -0700
To: think-c@rdatasys.com
From: rhartman@dsl2.uoregon.edu (Rick Hartmann)
Subject: Re: External editors
Hi,
Regarding the problem of external editors and Think Project Manager, there
is a new patch to Think Project Manager; now version 7.0.3. Check the
readme file. It fixes a variety of problems in previous releases. It is
being sent to the usual anon FTP sites, online services, and the Symantec
BBS. You can also download it from the Symantec Internet site:
devtools.symantec.com. This site is just a IIci limited to ten users so
access is sometimes difficult. Keep trying.
Rick
>From aland@cs.brandeis.edu 22 Jun 94 19:54:36 GMT
Path: ucivax!gateway
From: aland@cs.brandeis.edu ("Alan D.")
Subject: Re: Finder triangles
Message-ID: <9406221254.aa10530@q2.ics.uci.edu>
In-Reply-To: <9406220755.aa25243@q2.ics.uci.edu> from "Kevin O'Malley" at Jun 22, 94 02:55:51 pm
>From tslater@crl.nmsu.edu Sun, 26 Jun 1994 17:42:47 -0600
Return-Path: tslater@crl.nmsu.edu
Received: from lionfish.rdatasys.com (uucp@lionfish.rdatasys.com [198.232.168.1]) by wahoo.rdatasys.COM (8.6.9/8.6.9) with ESMTP id QAA13905 for <think-c@rdatasys.com>; Sun, 26 Jun 1994 16:42:57 -0700
Received: (from uucp@localhost) by lionfish.rdatasys.com (8.6.9/8.6.9) id QAA11489 for <think-c@rdatasys.com>; Sun, 26 Jun 1994 16:42:52 -0700
Received: from dns1.nmsu.edu(128.123.3.5) by lionfish.rdatasys.com via smap (V1.3mjr)
id sma011487; Sun Jun 26 16:42:50 1994
Received: from crl.nmsu.edu by NMSU.Edu (8.6.8.1/NMSU-1.18)
id RAA25833; Sun, 26 Jun 1994 17:42:47 -0600
Date: Sun, 26 Jun 1994 17:42:47 -0600
Message-Id: <199406262342.RAA25833@NMSU.Edu>
Received: by crl.nmsu.edu (4.1/SMI-4.1)
id AA07405; Sun, 26 Jun 94 17:42:44 MDT
From: tslater@crl.nmsu.edu (Ted Slater)
To: think-c@rdatasys.com
Subject: Object I/O with CStyleText
Hi All,
Can anyone supply me with a detailed example of how to implement
Object I/O for saving and reading a CStyleText object? Maybe even just
a CEditText example would help, but I'd rather see one for CStyleText.
Anyway, I've asked nearly everyone I could think of for help and have
been disappointed at every turn. And it's very important!! 8-]
Thanks!
Ted
>From msandri@netcom.com Thu Jun 30 16:59:58 PDT 1994
Received: from lionfish.rdatasys.com (uucp@lionfish.rdatasys.com [198.232.168.1]) by wahoo.rdatasys.COM (8.6.9/8.6.9) with ESMTP id QAA08670 for <think-c@rdatasys.com>; Thu, 30 Jun 1994 16:59:56 -0700
Received: (from uucp@localhost) by lionfish.rdatasys.com (8.6.9/8.6.9) id QAA15948 for <think-c@rdatasys.com>; Thu, 30 Jun 1994 16:59:54 -0700
Received: from netcom.netcom.com(192.100.81.100) by lionfish.rdatasys.com via smap (V1.3mjr)